SAP Web Dispatcher

Before adding a new system for SAP Web Dispatcher monitoring, you need to distinguish between the following supported monitoring scenarios for the SAP Web Dispatcher.

Monitoring the Remote SAP Web Dispatcher System

The monitoring connects to the SAP Web Dispatcher through the configured HTTP connection to the external server (type G RFC destination). The required data is collected for the monitoring through HTTP communication. For this reason, the prerequisite in this scenario is to have a configured valid HTTP destination as described in the chapter Configuring an HTTP Destination for the SAP Web Dispatcher.

Monitoring the Local SAP Web Dispatcher Running on the SAP System

The monitoring connects through the configured Internal or ABAP connection to the SAP system where the SAP Web Dispatcher is installed and running on the specific application server. The required data for the monitoring is collected through the preconfigured commands using the program wdispmon.

The prerequisite for this scenario is to have a configured valid Internal or ABAP connection that connects to the specific application server where the SAP Web Dispatcher is up and running. It is also necessary to determine the full path of the instance profile file of the SAP Web Dispatcher (mostly generated with the name "sapwebdisp.pfl").

Adding a New System for SAP Web Dispatcher Monitoring

Proceed as follows to add a new system for SAP Web Dispatcher monitoring:

1. Start transaction /DVD/MON.

2. In the application toolbar, click Add system (Shift+F1).

3. Select the main system type SAP Web Dispatcher.

4. Click Confirm.

• The screen System for SAP Web Dispatcher appears.

5. In the RFC destination field, enter a valid destination name. Only the connection types HTTP, Internal or ABAP are supported.

   • If you enter an Internal or ABAP connection, you also need to enter the full name (including the path) of the instance profile file for the SAP Web Dispatcher in the Instance profile field. For example, /usr/sap/sapwebdisp/sapwebdisp.pfl.

   • According to the provided RFC destination, the monitoring automatically determines the specific monitoring scenario and displays or hides the non-relevant fields for this specific scenario.

6. Click Check connection.

   • If an error occurs, the RFC destination or the name/path to the instance profile file is not configured correctly.

   • You can check and maintain the RFC destination by clicking Maintain destination or by starting transaction SM59.

• The required information is retrieved directly from the SAP Web Dispatcher and relevant fields pre filled automatically.

7. Optional: You can change the System description.

8. Optional: You can change the System name.

9. Click Confirm.

• A screen appears with the auto-detected server for the SAP Web Dispatcher instance.

10. Ensure that the Monitor flag is selected.

11. Click Confirm.

• The system for SAP Web Dispatcher monitoring has been added.

• You can start the monitoring by clicking Start default monitoring in the application toolbar. This starts the collector job with the profile WDISP_5MIN for the added system.

Configuring an HTTP Destination for the SAP Web Dispatcher

To communicate with the SAP Web Dispatcher and collect data, you must configure a valid HTTP destination for monitoring.

Proceed as follows to set up a valid configuration:

1. Start transaction SM59.

2. Click Create to create a new RFC destination.

3. In the RFC destination field, enter an RFC destination.

4. In Connection Type field, enter the value G (HTTP Connection to External Server).

5. In the Description field, enter a suitable description.

6. Go to the Technical Settings tab.

7. In the Target Host field, enter a valid target host.

8. In the Service No. field, enter a valid service number (port).

   • You can retrieve the host and port values from the URL, which is configured for SAP Web Dispatcher administration interface access.

9. In the Path Prefix field, enter a valid path prefix. This is the configured path for SAP Web Dispatcher administration interface access.

   You can also retrieve this path from the same URL as described above or from the configuration file sapwebdisp.pfl, which is available in the installation directory for the SAP Web Dispatcher.

10. Go to the Login & Security tab. For HTTP connections, proceed with step 11. For HTTPS connections, proceed with step 12.

11. For HTTP communication, the following details are required:

    1. Select the Basic Authentication option.

    2. In the Logon area, fill out all the fields for the SAP Web Dispatcher administration user.

12. For HTTPS communication, the following details are required:

    1. Select the Basic Authentication option.

    2. In the Logon area, fill out all the fields for the SAP Web Dispatcher administration user.

    3. In the SSL field, select Active.

    4. Assign a valid SSL Client Certificate. To do so, you must create an SSL Client Identity as described in the chapter Configuring the SSL Client Identity for an HTTPS Connection.

• The setup is complete.

Connection Test

Once you have configured all the required fields as detailed in the steps above, click Connection Test.

After the test execution, in the Test Result tab, you must receive an HTTP response status with the value 200. Otherwise, the configuration was not successful.

Configuring the SSL Client Identity for an HTTPS Connection

To add a certificate to SAP, create a new SSL client identity or use an existing SSL client identity (Anonymous or Standard) in transaction STRUST.

Creating a New SSL Client Identity

Proceed as follows to create a new SSL client identity:

1. Start transaction STRUST.

2. In the menu bar, click Environment > SSL Client Identities.

3. Click New Entries.

4. Enter an identity and a description.

5. Click Save.

6. Return to transaction STRUST.

7. Right-click the new SSL identity node and select Create to create a PSE file for a new SSL identity.

   • The Create PSE window opens.

8. Enter the required PSE options:

   • Name

   • Org. (Opt)

   • Comp./Org.

9. Click Confirm.

   • The new SSL client identity has been created.

Adding a Certificate to an SLL Client Identity

Proceed as follows to add a certificate to an SSL client identity:

1. Start transaction STRUST.

2. In the menu bar, click Certificate > Import.

   • The Import Certificate window opens.

3. In the File path field, select your certificate file, e.g. *.pem, *.cer, etc.

4. Click Confirm.

5. Double-click the used SSL client identity to load it.

   • You can now view the file content in the Certificate area.

6. Click Add to Certificate List.

7. Click Save.

   • The certificate has been added to the SSL client identity.